- Converted prev_resolved_at to a datetime from a timestamp in migration
- Added a method `should_send_email?` to determine if an email goes instead of a string of conditionals
- Cleaned up guard clauses
- Improved the datetime comparison in an AR query

The refactor involved removing a segment which forced a specific migration to run in favor of Rails' mechanism of alerting when migrations are pending. The prior method was too rigid and hard-coded. Now, the system still copies the migration over but doesn't automatically run it.

The 'prev_resolved_at' parameter has been removed from the error_params in the errors_controller, and subsequently from the error buttons in the views. Meanwhile, in the subscriber, 'prev_resolved_at' is now updated with the current 'resolved_at' before this is set to nil, maintaining the history of resolution times.

Simplified the condition check whether to send an email in SolidErrors::Occurrence. The method should_send_email? now has guard clauses if SolidErrors does not send emails or if no email recipient is set. Additionally, the instance method one_email_per_occurrence is renamed to one_email_per_occurrence? to follow the naming convention like `send_emails?`.

The config option that limits the email notifications to one email per error occurrence in the SolidErrors has been removed and, instead, that approach is used automatically (sending one per occurrence). Corrections were also made to the post-install message in the gemspec file to remove the ``*and* runs` from the note since we are not auto-running migrations.

…ng process

In the 'Occurrence' model, the condition checking if an error has only one occurrence has been simplified by replacing 'count == 1' with 'one?'. In the rake task, the file copying process from Solid Errors to Rails application has been altered so that instead of copying the file directly, it's named with a timestamp before copying to avoid potential naming conflicts. The migration file name was also simplified by removing the timestamp so that we can dynamically add one.

This patch replaces the original file existence check so that it now checks if there are any files with the same original filename (no timestamp) in the entire directory structure under the destination path. This avoids unnecessary file copy operations.

Don't need nested directory in glob

Co-authored-by: Stephen Margheim <stephen.margheim@gmail.com>

Co-authored-by: Stephen Margheim <stephen.margheim@gmail.com>

Co-authored-by: Stephen Margheim <stephen.margheim@gmail.com>

Added instructions to README file for running migration installer after updating the gem. Also, refactored 'solid_errors_tasks.rake' by simplifying the filename generation process during migration. These changes facilitate smoother gem updates and migrations.

This version (x.003) has changes that ensure the migration is copied to the containing application.

Introduced the `full_backtrace` configuration option for more granular control over logging error details. Removed unused migration files and rake tasks to simplify the codebase. Enhanced error handling by adding a backtrace cleaner to filter out irrelevant lines from logs.

Updated solid_errors gem from version 0.6.1 to 0.7.0 in Gemfile.lock. Adjusted the backtrace logic in subscriber.rb to correctly apply the backtrace cleaner only when needed.

Refine backtrace regex to support both single and double quotes. Add Ruby 3.4.0 to CI workflow for testing. Upgrade Nokogiri and SQLite3 to newer versions to ensure compatibility and performance improvements.

The actionmailer dependency was removed from solid_errors in the Gemfile.lock. This change ensures compatibility and reflects the updated requirements of the gem. Corrected an incorrect choice in a merge conflict

Corrected the use of the `error.backtrace` variable to `backtrace` in `lib/solid_errors/subscriber.rb` to ensure proper handling of backtrace data.

- Adjusted `should_send_email?` to reference `error.resolved_at` for consistency.
- Updated Gemfile.lock to use `solid_errors` version 0.7.3.
- Incremented gem version to 0.7.3.

- Refined `should_send_email?` to use `error.resolved?` for clarity.
- Updated Gemfile.lock to use `solid_errors` version 0.7.4.
- Incremented gem version to 0.7.4.

- Fixed incorrect reference of `self` in `send_email`, replacing it with `error` for consistency.
- Updated Gemfile.lock to use `solid_errors` version 0.7.5.
- Incremented gem version to 0.7.5.

…d_at`, and bump `solid_errors` to 0.8.0

- Refined `should_send_email?` to better handle resolved errors and new occurrences.
- Removed `resolved_at` reset logic in `send_email` for simplification.
- Introduced `prev_resolved_at` column to track previous resolution timestamps.
- Incremented gem version to 0.8.0.